Imo each test tests a specific functionality which requires a fixture set up for that. Its important that these figures mirror exactly how it would look in production or the tests are pointless.
For example customer A uses product A in a specific way it's important that we enter customerA.settings and productA.props into the test and only test the specifics in said transaction.
Companies that foster their juniors to first learn to solve problems on their own and then learn to use these tools to increase their output in a safe and efficient manner will most likely triumph over companies that seek to run an ai code farm.
It can help out a lot in writing base systems. I wanted to learn rust and made gpt write a game with me, it really could handle more complex things than I thought. For example it wrote a diablo style rotatable inventory system (cli, no graphic) which impressed me a lot.
Another game prototype i had lying around in react i asked Jules to refactor to use event sourcing rather than mutating values and I only had to give it a few pointers on what it had missed. It even found an old bug I had missed.
I guess nothing of it was really math heavy but that inventory grid was really solid
One thing that's common when having multiple sources like different data sources, cms and utility services is having a backend for frontend (BFF) which is what your frontend would call and in turn it would gather all your resources and format it the way your frontend expects it. The bff can cache the more static sources while proxying more dynamic ones.
This might be overkill for your project but it's a nice paradigm when you're dealing with multiple sources or sources that might change.
I brevet enjoyed the original. I found it tedious and repetitive with going into near identical hell holes to pick up rocks. Not too mention the leveling system, of all the janky TES leveling systems this might be the worst. The only thing I like with the original is the music.
I've ended up becoming the sole caretaker of two react native apps, something I did not ask for but some people were fried.
I'm not going to manually troubleshoot and learn everything that breaks when I need to update a dependency. I'll vibe through those errors, learn what I have time for and then test it like mad.
A lot of the time I end up having to solve things myself but my job wouldn't be tolerable if I had to manually work that shit.
There's also the issue that some android and iOS features don't work on rooted, like integrity check. We implemented it to prevent some malicious actors spamming our sms services, requiring them to use actual phones to access the service.
In the end we went with a captcha because we didn't want to exclude rooters but I can see it being a choice not all companies make.
Imo each test tests a specific functionality which requires a fixture set up for that. Its important that these figures mirror exactly how it would look in production or the tests are pointless.
For example customer A uses product A in a specific way it's important that we enter customerA.settings and productA.props into the test and only test the specifics in said transaction.